Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@packages/script/src/templates.ts`:
- Around line 242-255: The generated __registerGlobal currently destructures its
argument unguarded and throws when a hook deletes an entry; update
__registerGlobal (the function used to wrap useScript calls) to guard against a
missing/falsy input before destructuring (e.g. return undefined immediately if
!input or use a default param) so deleted entries from __globals don't crash
plugin setup; keep the existing checks for enabled/empty/null src and ensure
call sites in the setupBody that build __globals and globalInits remain
compatible. Also update the inline snapshot and the unit tests in
test/unit/templates.test.ts to reflect the new behavior and add a test case for
a deleted/global entry.
- Around line 248-257: The current implementation builds registrations only from
the static config.globals (globalMapEntries/globalInits) and never handles keys
added by the runtime hook after await nuxtApp.hooks.callHook('scripts:globals',
__globals); update templates.ts so that immediately after calling the hook you
re-scan Object.keys(__globals) and for any key not already handled push a
registration/init that calls __registerGlobal(__globals["<key>"], ...) (add to
globalInits or inits as appropriate) and ensure the final provide.scripts list
is derived from Object.keys(__globals) combined with resolvedRegistryKeys
instead of only Object.keys(config.globals), so runtime-added keys are
registered and exposed; retain existing behavior for statically declared keys
and document/type-note that bundlers/types remain static.
- Around line 29-31: The generated type for the 'scripts:globals' hook is
currently a closed object with required properties, causing TS2790 when
deleting/adding keys; update the template in packages/script/src/templates.ts
that builds the 'scripts:globals' signature so each mapped key is optional (e.g.
use `?:`) and include an index signature like `[key: string]: Record<string,
any>` so unknown additions and deletions type-check; adjust the globalsKeys.map
generation to emit optional properties and append the index signature to the
produced object type.

---

Nitpick comments:
In `@test/e2e/issue-759-globals-env-override.test.ts`:
- Around line 33-39: Add an assertion to the test that verifies the
runtime-registered $scripts.scrads value was updated by the scripts:globals hook
by reading the DOM element rendered by app.vue with id "`#scrads-src`" (exposed in
the app) and asserting its text/content equals
"https://scrads.example/from-hook.js"; keep existing HTML head assertions but
add this extra check so $scripts.scrads is validated as rewritten at runtime.

In `@test/fixtures/issue-759/plugins/globals.ts`:
- Line 6: Remove the explicit type annotation on the callback parameter so the
hook callback can infer the real "scripts:globals" hook type; locate the
nuxtApp.hooks.hook call (nuxtApp.hooks.hook('scripts:globals', (globals:
Record<string, Record<string, any>>) => { ... })) and change it to use an
untyped parameter (e.g., (globals) => { ... }) so the fixture exercises the
generated Nuxt hook contract rather than masking it.

In `@test/unit/templates.test.ts`:
- Around line 342-361: Add a test asserting the deleted/undefined entry case by
adding expect(__registerGlobal(undefined, {})).toBeUndefined() to the
"__registerGlobal skips disabled entries and registers the rest" test, and
ensure the implementation of __registerGlobal in templates.ts defensively
handles an undefined input (e.g., early return before destructuring) so it no
longer throws when called with undefined.

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Outside diff comments:
In `@test/unit/templates.test.ts`:
- Around line 319-322: Update the test comment for "globals are passed through
the scripts:globals runtime hook before registration" to reflect the actual
runtime-hook contract: the generated plugin only registers statically declared
keys so the hook may rewrite or delete existing entries on __globals but cannot
add brand-new keys that will be registered; reference the scripts:globals
runtime hook and __globals in the comment so readers know additions won't be
picked up by the static registration.